AI can generate a thousand articles a minute. But it can't do your thinking for you. Hashnode is a community of builders, engineers, and tech leaders who blog to sharpen their ideas, share what they've learned, and grow alongside people who care about the craft.
Your blog is your reputation — start building it.
8h ago · 3 min read · Harvard Health Hackathon National Round — Our Journey with HPass Proud to have participated in the Harvard Health Hackathon National Round held at NTIC, Kathmandu University. After qualifying from Asp
Join discussion
1h ago · 3 min read · What is hybrid search? Hybrid search combines full-text and vector queries into a single request, running against an index that holds both plain-text content and generated embeddings. Vector search ex
Join discussion
59m ago · 8 min read · A blog post on LangChain's site about how Madrigal Pharmaceuticals built their multi-agent AI platform caught my attention this week. Not because of the architecture — orchestrator routing, parallel a
Join discussion
7h ago · 8 min read · REST API Design with Express.js: A Practical Guide to Resources, Routes, and HTTP Methods TL;DR: REST is a set of conventions for structuring HTTP APIs around resources. This guide walks through what those conventions are, why they exist, and how to ...
Join discussion
Obsessed with crafting software.
4 posts this monthcloud native and K8s things
1 post this monthTrying to put engineering back into software development
1 post this monthFull Stack Engineer
2 posts this monthCNCF Ambassador, multi cloud, Influx ACE, Rancher, Kubernetes guy
1 post this monthObsessed with crafting software.
4 posts this monthcloud native and K8s things
1 post this monthTrying to put engineering back into software development
1 post this monthFull Stack Engineer
2 posts this monthCNCF Ambassador, multi cloud, Influx ACE, Rancher, Kubernetes guy
1 post this monthThis hits the core issue. AI can generate structure fast, but it doesn’t hold intent. So you get something that “works,” but doesn’t always align with why it exists or how it should evolve. That’s why the bottleneck shifts from building to guiding.
The traffic manager analogy for the Event Loop is a good one. I usually explain it to new engineers as a restaurant kitchen with one chef: the chef does not stand at the oven watching a dish cook — they hand it off, move to the next order, and come back when it is ready. The moment the chef starts watching the oven is when the whole kitchen backs up. Same thing happens when you block the Event Loop. Nice post, solid foundation for anyone learning Node internals.
Yes, I’d separate them in most serious setups. CI should prove the code is safe to merge. CD should control how and when it reaches users. Keeping them separate makes rollbacks, approvals, staging checks, and production releases much easier to manage.
I’m trying to understand how different teams structure their delivery process. In many setups, CI handles everything (builds, deployments, approvals, sometimes even rollback logic). It works, but over
Yes, I’d separate them in most serious setups. CI should prove the code is safe to merge. CD should control how and when it reaches users. K...
In simpler teams, CI/CD is kept in one pipeline because it’s easier to manage and faster to ship. But as systems grow, separating concerns h...
